Skip to content

Conversation

@tomcat323
Copy link
Contributor

@tomcat323 tomcat323 commented Jan 24, 2025

Problem

Our release MCM currently has a step for each extension (Toolkit and Q) that requires the human operator to wait and check for the marketplace publish and then try to install from the marketplace. This uses human time and can easily be automated.

Solution

Added a final stage in release pipeline: https://code.amazon.com/reviews/CR-173945904/revisions/1#/commits

that runs this YML build script that automatically installs and uninstalls the extension from marketplace on a two minute interval.

When the version matches the new release version, the code-build succeeds:
Screenshot 2025-01-23 at 2 44 45 PM

When it doesn't, it keeps retrying until the timeout limit is reached (1 hour):
Screenshot 2025-01-23 at 4 52 07 PM


  • Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
  • Your code changes must meet the guidelines in CONTRIBUTING.md.
  • License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@github-actions
Copy link

  • This pull request implements a feat or fix, so it must include a changelog entry (unless the fix is for an unreleased feature). Review the changelog guidelines.
    • Note: beta or "experiment" features that have active users should announce fixes in the changelog.
    • If this is not a feature or fix, use an appropriate type from the title guidelines. For example, telemetry-only changes should use the telemetry type.

@tomcat323 tomcat323 changed the title feat: check marketplace update in release feat(release): check marketplace update in release Jan 24, 2025
@tomcat323 tomcat323 changed the title feat(release): check marketplace update in release feat(release): check marketplace update Jan 24, 2025
@tomcat323 tomcat323 changed the title feat(release): check marketplace update feat(release): check for marketplace update Jan 24, 2025
@tomcat323 tomcat323 marked this pull request as ready for review January 24, 2025 16:26
@tomcat323 tomcat323 requested a review from a team as a code owner January 24, 2025 16:26
@tomcat323 tomcat323 merged commit 2200b15 into aws:master Jan 27, 2025
26 checks passed
tomcat323 added a commit that referenced this pull request Feb 1, 2025
## Problem
in #6426, a new release
pipeline stage was added that checks the marketplace extension has been
updated. This PR addes a stage check and only look for an existing
version of the extension when in BETA.

Output in beta:
<img width="1074" alt="Screenshot 2025-01-30 at 12 45 07 PM"
src="https://github.com/user-attachments/assets/ee0b8df7-cd89-4e44-a99b-9746134a8aa9"
/>

unblocks: https://pipelines.amazon.com/pipelines/AWSVSCodeInfrastructure

---------

Co-authored-by: tomzu <[email protected]>
s7ab059789 pushed a commit to s7ab059789/aws-toolkit-vscode that referenced this pull request Feb 19, 2025
## Problem
Our release MCM currently has a step for each extension (Toolkit and Q)
that requires the human operator to wait and check for the marketplace
publish and then try to install from the marketplace. This uses human
time and can easily be automated.

## Solution
Added a final stage in release pipeline:
https://code.amazon.com/reviews/CR-173945904/revisions/1#/commits

that runs this YML build script that automatically installs and
uninstalls the extension from marketplace on a two minute interval.

When the version matches the new release version, the code-build
succeeds:
<img width="768" alt="Screenshot 2025-01-23 at 2 44 45 PM"
src="https://github.com/user-attachments/assets/93f80a6d-573c-4524-995c-6491ecf1fb6f"
/>


When it doesn't, it keeps retrying until the timeout limit is reached (1
hour):
<img width="694" alt="Screenshot 2025-01-23 at 4 52 07 PM"
src="https://github.com/user-attachments/assets/c5433383-1194-4ec4-845a-4e63d8959cf7"
/>

---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

---------

Co-authored-by: tomzu <[email protected]>
s7ab059789 pushed a commit to s7ab059789/aws-toolkit-vscode that referenced this pull request Feb 19, 2025
## Problem
in aws#6426, a new release
pipeline stage was added that checks the marketplace extension has been
updated. This PR addes a stage check and only look for an existing
version of the extension when in BETA.

Output in beta:
<img width="1074" alt="Screenshot 2025-01-30 at 12 45 07 PM"
src="https://github.com/user-attachments/assets/ee0b8df7-cd89-4e44-a99b-9746134a8aa9"
/>

unblocks: https://pipelines.amazon.com/pipelines/AWSVSCodeInfrastructure

---------

Co-authored-by: tomzu <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants